Repository navigation
build: keep pnpm-workspace.yaml to the workspace list (directory blocker) - #38
Merged
Merged
Conversation
Anthropic's plugin directory blocks plugins/refkit ("Package registry
redirected") because pnpm-workspace.yaml above it carried a pnpm setting
(onlyBuiltDependencies: esbuild). esbuild resolves its platform binary from its
optional dependency, so its install script isn't needed. plugin-manifest pins
that nothing between the repo root and the plugin configures a package manager.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Anthropic's plugin directory validation blocks
plugins/refkitwith this finding:The directory treats every pnpm setting in a
pnpm-workspace.yamlabove a plugin that runsnpxas a possible redirect. Here the only setting wasonlyBuiltDependencies: [esbuild].What changes
pnpm-workspace.yamlkeeps onlypackages.onlyBuiltDependencies: [esbuild]is removed. esbuild gets its platform binary from its optional@esbuild/<platform>dependency, so its install script isn't needed. pnpm now prints "Ignored build scripts: esbuild" on install.plugin-manifesttests check two things:pnpm-workspace.yamldeclares onlypackages;.npmrc,bunfig.tomloruv.tomlat the repo root or inplugins/.Verification
On a clean
pnpm install --frozen-lockfilein a fresh worktree:@esbuild/darwin-arm64was installed.typecheck,lintandbuildpass.test:run: 658 passed, 25 skipped.smoke:artifactpasses all 3 scenarios: pack, clean npm install, and booting the MCP CLI.After merge, use Re-validate in the developer portal. Expected outcome: no blocking findings, and the pinned-npx policy hold remains.